Searched hist:"8 f92938f" (Results 1 – 3 of 3) sorted by path
| /freebsd/sbin/nvmecontrol/ |
| H A D | ns.c | 8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
|
| H A D | passthru.c | 8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
|
| H A D | reset.c | 8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
8f92938f Wed Oct 28 17:28:48 GMT 2020 Alexander Motin <mav@FreeBSD.org> Use proper variable for device path.
It seems *-passthru commands were broken from the day one, since the
device path is fetched into opt.dev variable and not left in argv[optind].
The other three wrong argv[optind] instances are just in error messages.
MFC after: 1 week
Sponsored by: iXsystems, Inc.
|